Fast data-link connection method for saving connection time in CDMA 2000 network

ABSTRACT

Disclosed herein is a fast data call connection method capable of reducing a connection time and increasing the probability of connection success in a CDMA 2000 network. 
     In the fast data call connection method of the present invention, the PDSN transmits a data call connection request message, including an authentication type and a challenge value, to the MS. The MS transmits a data call connection response message, including a response to the challenge value, to the PDSN. The PDSN performs authentication with reference to the data call connection response message, and transmits a data call connection complete message to the MS if authentication succeeds. Accordingly, the present invention is advantageous in that it can reduce connection time, can increase the probability of connection success, and can guarantee compatibility by checking the MS version before a data call connection process is executed.

CROSS REFERENCE TO RELATED APPLICATION

This application is the National Phase application of InternationalApplication No. PCT/KR2006/002369, filed Jun. 20, 2006, which designatesthe United States and was published in English. This application, in itsentirety, is incorporated herein by reference.

TECHNICAL FIELD

The present invention relates, in general, to a data call connectionmethod for reducing connection time in a CDMA 2000 network and, moreparticularly, to a fast data call connection method for reducingconnection time in a CDMA 2000 network, which eliminates an unnecessaryprocedure from a conventional PPP negotiation process, and minimizes thenumber of messages, thus reducing connection time and increasing theprobability of connection success.

BACKGROUND ART

Recently, as the development of the mobile communication environment ispredicted to be highly likely, the market requirement for continuousfast access to the mobile Internet has increased. However, although aCode Division Multiple Access (CDMA) network has developed into CDMA2000 networks, for example, CDMA2000 1X and Evolution Data Optimized(EV-DO) (High Rate Packet Data: HRPD) networks, the initial connectiontime has not improved. Such a delay in initial connection time acts as afactor causing dissatisfaction in users provided with WirelessApplication Protocol (WAP) services over the CDMA 2000 networks. Serviceproviders reduce the apparent connection time, as perceived by users, bystoring cache in terminal memory.

However, network service providers do not currently detect a method forimproving Point-to-point protocol (PPP) connection time, which isstandardized in the 3rd Generation Partnership Project 2 (3GPP2)standards. For PPP negotiation in CDMA 2000 networks, a minimum of 13messages are exchanged between peers even if parameters are optimizedbetween a Mobile Station (MS) and a Packet Data Service Node (PDSN).

That is, referring to the PPP negotiation process shown in FIG. 1,request messages for link configuration (LCP Configuration Request) andacknowledgment messages to the link configuration request (LCPConfiguration Ack) should be exchanged between an MS and a PDSN in aLink Control Protocol (LCP) state, so that a total of four messages aretransmitted and received at steps S001 to S004. Even in a ChallengedHandshake Authentication Protocol (CHAP) authentication procedure, threemessages should be exchanged at steps S005 to S007. Further, in anInternet Protocol (IP) Control Protocol (IPCP) negotiation procedure, amessage (Nak), required to assign an IP address and a Domain Name Server(DNS) address to the MS, is added, so that a minimum of 6 messagesshould be exchanged at steps S008 to S013.

Problems occurring according to the characteristics of a wirelessnetwork in the above procedure are described as follows.

First, when the state of a wireless network is bad, messages may belost. If an acknowledgement response message (Ack) is lost, statusinconsistency occurs between both peers, so that there is a probabilitythat the peers may fall into a loop, and such a phenomenon actuallyoccurs in a CDMA 2000 network.

Second, there is no need to use all of the options used for PPPconnection in respective states. Actually, an option necessary for aCDMA 2000 network at a Link Control Protocol (LCP) step is only anoption related to an authentication method.

Third, there is a problem in that a normal connection time longer than 1second is required in order to perform a procedure of exchanging a lotof messages for the negotiation of options that are not required for theCDMA 2000 network, as described above.

DISCLOSURE OF THE INVENTION

Accordingly, the present invention has been made keeping in mind theabove problems occurring in the prior art, and an object of the presentinvention is to provide a data call connection method for reducingconnection time in a CDMA 2000 network, which exchanges only a minimalnumber of messages between an MS and a PDSN at the time of connecting adata call in the CDMA 2000 network. This improves on a conventional PPPconnection method in the CDMA 2000 network, so that the authenticationof the MS and the assignment of an IP address can be performed, thusrealizing fast data call connection.

Another object of the present invention is to provide a data callconnection method, which checks information about the version of an MSat the time of connecting a data call in a CDMA 2000 network, andperforms a negotiation procedure suitable for the version of the MS,thus providing compatibility with an existing MS.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flow diagram of a conventional PPP negotiation process fordata call connection;

FIG. 2 is a flow diagram of a fast data call connection processaccording to an embodiment of the present invention;

FIG. 3 is a flow diagram showing a mobile IP procedure in the data callconnection process according to the present invention;

FIGS. 4A and 4B are flow diagrams showing a procedure for checking theversion of an MS to provide backward compatibility in the data callconnection method according to the present invention; and

FIGS. 5 to 7 are flow diagrams showing an authentication procedure fordata call connection according to the present invention.

BEST MODE FOR CARRYING OUT THE INVENTION

In accordance with an aspect of the present invention to accomplish theabove objects, there is provided a fast data call connection methodbetween a Mobile Station (MS) and a Packet Data Service Node (PDSN) in aCode Division Multiple Access (CDMA) 2000 network, comprising a firststep of the PDSN transmitting a data call connection request message,including an authentication type and a challenge value, to the MS; asecond step of the MS, having received the data call connection requestmessage, transmitting a data call connection response message, includinga response to the challenge value, to the PDSN; and a third step of thePDSN performing authentication with reference to the data callconnection response message, and transmitting a data call connectioncomplete message to the MS if authentication succeeds.

In accordance with another aspect of the present invention, there isprovided a fast data call connection method between a Mobile Station(MS) and a Packet Data Service Node (PDSN) in a Code Division MultipleAccess (CDMA) 2000 network, comprising a first step of the PDSNtransmitting a data call connection request message, including a ClearText authentication type, to the MS; a second step of the MS, havingreceived the data call connection request message, transmitting a datacall connection response message, including an authentication requestvalue, to the PDSN; and a third step of the PDSN performingauthentication with reference to the data call connection responsemessage, and transmitting a data call connection complete message to theMS if authentication succeeds.

In accordance with a further aspect of the present invention, there isprovided a fast data call connection method between a Mobile Station(MS) and a Packet Data Service Node (PDSN) in a Code Division MultipleAccess (CDMA) 2000 network, comprising a first step of the PDSNtransmitting a data call connection request message, including anauthentication type, to the MS; a second step of the MS, having receivedthe data call connection request message, transmitting a data callconnection response message, including a no-authentication request, tothe PDSN; and a third step of the PDSN transmitting a data callconnection complete message to the MS.

Hereinafter, embodiments of the present invention will be described indetail with reference to the attached drawings.

FIG. 2 is a flow diagram of a data call connection process according toan embodiment of the present invention, which shows a data callconnection process executed in response to a request from a Packet DataService Node (PDSN).

A data call connection process according to the present invention is anoperating procedure for a new protocol that has been proposed to improveon the conventional PPP connection process. For the convenience ofdescription, the protocol proposed in the present invention isdesignated as a Fast Data-Link Connection Protocol (FDCP), and isdescribed below.

As shown in the drawing, the data call connection process of the presentinvention performs data connection through the transmission/reception ofthree messages between a Mobile Station (MS) and a PDSN, the detailedprocedure therefor being described below.

First, the PDSN transmits an FDCP request message (FDCP Request) to theMS as an initial message at step S101.

Table 1 shows an example of items included in the FDCP request message.In Table 1, TLV denotes which part of Type/Length(Octet)/Value isincluded in each item, and Presence denotes whether each item ismandatory (M), optional (O), or conditional (C).

TABLE 1 Type ID Field/option Description TLV Presence Length FDCP HeaderFDCP header — M 13 0011H Authentication Authentication TLV O ≧4parameter parameter 0015H External External TLV O ≧4 authenticationauthentication protocol protocol

As shown in Table 1, the FDCP request message may include anauthentication parameter, and is composed of an authentication parameterID field (T), a data length field (L), and an actual data field (V). Theformat of the authentication parameter is shown in the following Table2.

authentication parameter ID authentication parameter lengthAuthentication type Authentication data length Authentication data value

In Table 2, the authentication parameter ID can be ‘0011H’, as shown inTable 1, and the length of the authentication parameter is the totallength of the authentication parameter. Further, authentication type maybe one of Message Digest 5 (MD5), One Time Password (OTP) and Clear-Text(unencrypted authentication). If the authentication type (T) is MD5, anauthentication data value (V) can be an MD5-challenge value, whereas ifthe authentication type (T) is OTP, the authentication data value (V)can be an OTP-challenge value.

Table 3 shows the description of each authentication type and the typeof authentication data value included in authentication parameters.

TABLE 3 Authentication type Description Authentication data value 00HMD5(Default) MD5-challenge value 01H OTP OTP-challenge value (algorithmidentifier, seed, serial number) 02H Clear Text None

In an embodiment of the present invention, when transmitting an FDCPrequest message to the MS, the PDSN can transmit an FDCP requestmessage, with an authentication type and an authentication data value(that is, a challenge value) being included in the FDCP request message(that is, MD5 or OTP authentication is requested), or with only anauthentication type being included in the FDCP request message (that is,unencrypted authentication is requested). As described later, the MStransmits different FDCP response messages depending on whether both anauthentication type and a challenge value are included in an FDCPrequest message and whether only an authentication type is included inan FDCP request message, and depending on the authentication type thatcan be supported by the MS.

Meanwhile, the FDCP request message can also include an externalauthentication protocol. The external authentication protocol can be oneof Extensible Authentication Protocol (EAP), PPP Authentication Protocol(PAP), and Challenge-Handshake Authentication Protocol (CHAP). Theexternal authentication protocol is composed of an authenticationprotocol ID field (T), a data length field (L) and an actual data field(V).

With the development of wireless data services, the function ofauthenticating a subscriber's authority in the CDMA 2000 network hasgradually increased in importance, and thus some authenticationprocedure is required. When an external authentication mode is used, itis preferable to use CHAP because PAP carries a possibility of apassword being leaked, and is low in security.

The MS, having received the FDCP request message, transmits an FDCPresponse message (FDCP Ack) at step S103. The FDCP response message caninclude items shown in Table 4.

TABLE 4 Type ID Field/Option Description TLV Presence Length FDCP HeaderFDCP header — M 13 0001H MRU Maximum reception unit TV O 4 0002H IPv4Address IPv4 address TV O 6 0003H IPv6 Address IPv6 address TV O 180004H IPv4 Primary DNS Address IPv4 primary DNS TV O 6 address 0005HIPv4 Secondary DNS Address IPv4 secondary DNS TV O 6 address 0006H IPv6Primary DNS Address IPv6 primary DNS TV O 18 address 0007H IPv6Secondary DNS Address IPv6 secondary DNS TV O 18 address 0012H ClearText Authentication Unencrypted TLV C ≧5 Request authentication request0013H MD5-Challenge Response MD5-Challenge TLV C 20 authenticationresponse 0014H OTP-Challenge Response OTP-Challenge TLV C ≧5authentication response 0023H No Authentication No authentication T C 1

With reference to Table 4, examples of items that can be included in theFDCP response message are described as follows.

The MS can request any one of the authentication algorithms, such asMD5, OTP, and Clear-Text, or can request no-authentication. The MS cantransmit an FDCP response message, including any one of MD5-challengeresponse option, OTP-challenge response option, Clear-Textauthentication request option, and a no-authentication option, dependingon the authentication type included in the FDCP request message. Eachoption for an authentication request is composed of an option ID field(T), a data length part (L), and an actual data field (V).

In an embodiment of the present invention, if an authentication type andan authentication data value (that is, a challenge value) are includedin the FDCP request message transmitted at step S101, the MS transmitsan FDCP response message, with a response (MD5-Challenge Response) tothe challenge being included in the FDCP response message. That is, whenthe PDSN designates an authentication type as MD5, and transmits an FDCPrequest message with MD5-challenge included in the FDCP request message,the MS transmits an FDCP response message including a response to theMD5 challenge. When the PDSN designates an authentication type as OTP,and transmits an FDCP request message with OTP-challenge included in theFDCP request message, the MS transmits an FDCP response messageincluding a response to the OTP challenge (OTP-Challenge Response).

In another embodiment of the present invention, when a Clear Textauthentication type is included in an FDCP request message, the MStransmits an FDCP response message with an authentication request valueincluded in the FDCP response message. That is, when the PDSN designatesan authentication type as Clear Text, the PDSN includes anauthentication request value, for example, a peer ID and a password, inan FDCP request message, and transmits the FDCP request message.

In a further embodiment of the present invention, the MS can transmit anFDCP response message requesting no-authentication, regardless of theauthentication type included in the FDCP request message.

Meanwhile, the MS can support any one of the external authenticationalgorithms, such as EAP, PAP and CHAP. In this case, an externalauthentication request algorithm that can be supported is included inthe no-authentication field of an FDCP response message, and the FDCPresponse message can be transmitted. When the MS supports an externalauthentication algorithm, the transmission/reception of additional FDCPmessages is required between the MS and the PDSN, and a detaileddescription thereof will be provided later with reference to FIGS. 5 to7.

Next, a Maximum Receive Unit (MRU) option is a field for defining themaximum length of an IP packet. If the MRU option is not included in anFDCP response message, the length of an IP packet is determined to be adefault value (for example, 1500 bytes).

Further, an FDCP response message can include an Internet ProtocolVersion 4 (IPv4) address or an IPv6 address depending on whether the MSsupports IPv4 or IPv6. When an IP address, IPv4 or IPv6 (or can alsorefer to ‘IP address option’), is included in an FDCP response message,the FDCP response message may include a primary DNS address or asecondary DNS address. When an IP address is not included in an FDCPresponse message, it is considered that the MS supports a mobile IPaddress.

As an IP address, a simple IP address or a fixed IP address can be used.If the MS supports simple IPv4 or simple IPv6, the MS transmits an FDCPresponse message, with an IP address set to 0, at the time oftransmitting an FDCP response message, thus requesting the assignment ofan address. For example, in the case of IPv4, the address can be set to0.0.0.0. In contrast, when the MS supports fixed IPv4 or fixed IPv6, theMS includes an IP address and a DNS address, which have been previouslyassigned and stored, in the IP address and DNS address fields of an FDCPresponse message, and transmits the FDCP response message. In this case,the term “simple IP connection” means the case where a temporary IPaddress is assigned upon each connection.

For example, when the MS attempts an IPv6 call, the MS transmits an IPaddress with an IPv6 address included in the IP address. For example,when a call is attempted using a mobile IP, the MS transmits an FDCPresponse message without including an IP address in the FDCP responsemessage, thus transmitting to the PDSN the fact that a call is beingattempted using a mobile IP.

Although not shown in the drawing, it is preferable that, aftertransmitting an FDCP request message to the MS at step S101, the PDSNoperates a timer, and releases a session if an FDCP response message isnot received from the MS within a preset period.

Further, as the result of the examination of an authentication parameteroption, included in the FDCP request message, by the MS having receivedthe FDCP request message from the PDSN, if no authentication mode thatcan be supported exists, the MS transmits an FDCP reject message (FDCPReject), including the cause of rejection, rather than an FDCP responsemessage, to the PDSN, and thus the PDSN releases the session.

After the FDCP response message has been transmitted to the PDSN fromthe MS at step S103, the PDSN authenticates the MS with reference to anauthentication request option included in the FDCP response message, andtransmits an FDCP complete message (FDCP Complete) at step S105 ifauthentication succeeds. If authentication fails after the PDSN receivesthe FDCP response message from the MS at step S103, it is preferablethat the PDSN transmit an FDCP reject message (FDCP Reject) to the MSand release the session.

In detail, the PDSN, having received the FDCP response message, performsauthentication with reference to an authentication request optionincluded in the FDCP response message transmitted by the MS. When thePDSN transmits an MD5 authentication type and an MD5 challenge value atstep S101, and the MS transmits a response to the MD5 challenge at stepS103, the PDSN performs authentication using the response to the MD5challenge. Similarly, when the PDSN transmits an OTP authentication typeand an OTP challenge value at step S101, and the MS transmits a responseto the OTP challenge at step S103, the PDSN performs authenticationusing the response to the OTP challenge. When the PDSN transmits a ClearText authentication type at step S101 and the MS transmits anauthentication request value required for Clear Text authentication (forexample, a peer ID, a password, etc.) at step S103, the PDSN performsauthentication using the authentication request value. However, when theMS requests no-authentication at step S103, the authentication procedurecan be omitted.

Table 5 shows examples of the items included in an FDCP completemessage.

TABLE 5 Type ID Field/option Description TLV Presence Length FDCP HeaderFDCP header — M 13 0002H MS IPv4 Address IPv4 address TV O 6 0003H MSIPv6 Address IPv6 address TV O 18 0004H IPv4 Primary DNS Address IPv4primary DNS TV O 6 address 0005H IPv4 Secondary DNS Address IPv4secondary DNS TV O 6 address 0006H IPv6 Primary DNS Address IPv6 primaryDNS TV O 18 address 0007H IPv6 Secondary DNS Address IPv6 secondary DNSTV O 18 address 0008H PDSN IPv4 Address IPv4 address TV O 6 0009H PDSNIPv6 Address IPv6 address TV O 18 0010H IP Compression Protocol IPcompression protocol TLV O ≧4

Referring to FIG. 5, an FDCP complete message can include an IP address(or can also refer to ‘IP address option’) and a DNS address (or canalso refer to ‘DNS address option’). The FDCP complete message isassigned differently depending on whether the IP address is a simple IPaddress or fixed IP address, and has different formats corresponding toIPv4 or IPv6.

For example, when the MS supports simple IPv4 or simple IPv6, the PDSNassigns an IP address and primary/secondary DNS addresses, includes theassigned addresses in the IP address field and primary/secondary DNSaddress fields of an FDCP complete message, and then transmits the FDCPcomplete message. When the MS supports fixed IPv4 or IPv6, the PDSNincludes the IP address and primary/secondary DNS addresses, which havebeen included in the FDCP response message by the MS and transmitted bythe MS, in the IP address field and primary/secondary DNS address fieldsof an FDCP complete message, without change, and then transmits the FDCPcomplete message.

If the MS supports simple IPv4 or simple IPv6, but the PDSN does nothave an assignable IP address, the PDSN transmits an FDCP reject message(FDCP Reject), including the cause of rejection, to the MS, and releasesthe session. Further, when the MS supports fixed IPv4 or fixed IPv6, andtransmits an FDCP response message, with an IP address and a DNS addressbeing included in the FDCP response message, the PDSN determines whetherthe transmitted IP address is authentic. If the IP address is determinedto be authentic, the PDSN performs a subsequent procedure, whereas, ifthe IP address is determined to be inauthentic, the PDSN transmits anFDCP reject message (FDCP Reject) to the MS, and releases a session.

Meanwhile, when an IP address is not included in the FDCP responsemessage, the PDSN recognizes that a current call is a mobile IP call,transmits an FDCP complete message without including an IP address and aDNS address in the FDCP complete message, and performs a mobile IP callconnection procedure. This procedure will be described later withreference to FIG. 3.

Referring to Table 5 again, the FDCP complete message may furtherinclude an IP compression protocol option. This is an option requiredwhen IP compression is supported, and is composed of an option IP field,an option length field, an IP compression protocol IP field, and anactual data field. The IP compression protocol can be one of RobustHeader Compression (ROHC), regular IP data, compression TransmissionControl Protocol/Internet Protocol (TCP/IP), and decompression TCP/IP.

When a compression protocol option is included in an FDCP completemessage, the MS and the PDSN transmit or receive compressed packet datadepending on the compression protocol specified by the compressionprotocol option in a subsequent IP communication procedure.

When the IP connection procedure is completed through the aboveprocedure, IP communication starts at step S107.

Although not shown in the drawing, the MS and the PDSN may add one ortwo FDCP messages when another option, not described above, is added.For example, in order to determine whether an Always-On option isactivated, the PDSN transmits an FDCP keep-alive message(FDCP_KEEP_ALIVE) to the MS after transmitting the FDCP completemessage. If a response message to the FDCP keep-alive message(FDCP_KEEP_ALIVE ACK) is received from the MS, the PDSN maintains anFDCP session in an activated state.

FIG. 3 is a flow diagram showing a mobile IP procedure in the data callconnection process according to the present invention.

When the MS supports a mobile IP, options related to an IP address and aDNS address are not included in an FDCP response message or an FDCPcomplete message, as described above. After FDCP session negotiation hasbeen performed, a separate procedure for mobile IP service isindependently performed.

FIG. 3 illustrates a mobile IP procedure after the FDCP sessionnegotiation has been performed at steps S101 to S105. After transmittingthe FDCP complete message, the PDSN transmits a router notificationmessage (Agent Advertisement) to the MS at step S201. Thereafter, if theMS requests location registration (Registration Request) at step S203,the PDSN performs location registration on the MS and transmits alocation registration reply message (Registration Reply) to the MS atstep S205, so that the mobile IP procedure is completed, and a mobile IPcall is initiated at step S107.

At step S205, since the PDSN includes an IP address, existing in thehome address region of a corresponding MS, in a location registrationreply message, and transmits the location registration reply message, aseparate IP address is not used during a previous session negotiationprocedure.

As described above, the present invention omits an unnecessary step froma conventional PPP negotiation procedure, or simultaneously performscorresponding steps when a data call is connected in a CDMA 2000network, thus reducing connection time.

Such a negotiation procedure may be supported or not supported dependingon the version of the MS. For this operation, the present inventionchecks version information of the MS before the negotiation procedure isperformed, thus performing a control operation so that either anegotiation procedure according to the present invention or aconventional PPP negotiation procedure is performed.

FIGS. 4A and 4B are flow diagrams showing a procedure for checking theversion of an MS to provide backward compatibility in the data callconnection method according to the present invention.

In the present invention, the MS transmits MS version information to thePDSN through a base station controller (or an access network) whenconnecting a call for packet data service. The PDSN, having received theMS version information, checks the MS version information. If the MS isdetermined to be an MS that supports FDCP, the PDSN performs thenegotiation procedure of FIG. 2, otherwise, the PDSN performs aconventional PPP negotiation procedure.

First, FIG. 4A is a flow diagram showing a procedure for checking theversion of an MS to provide compatibility with an existing MS in aCDMA2000 1X network. The MS can transmit service option 7 x, which is anew service option assigned to indicate that the MS is anFDCP-supporting MS, when performing a service option negotiationprocedure with the PDSN at step S300. The PDSN, having received theservice option 7 x, recognizes that the corresponding MS is an MS towhich FDCP can be applied, and performs the FDCP connection procedureincluding steps S101 to S105 of FIG. 2.

Although not shown in the drawing, an MS that does not support an FDCPconnection procedure transmits service option 33 to the PDSN. In thiscase, the PDSN performs a conventional PPP negotiation procedure.

Meanwhile, FIG. 4B is a flow diagram showing a procedure for checkingthe version of an MS to provide compatibility with an existing MS in aCDMA2000 HRPD network. The MS transmits a protocol ID when performingsession negotiation with an Access Network (AN) at step S401. After thesession negotiation between the MS and the access network (AN) has beencompleted at step S403, the AN transmits service 7 y, which is a newservice option assigned to indicate that the MS is an FDCP-supportingMS, with reference to the protocol ID received from the MS at step S405when the AN and the PDSN perform a service option negotiation procedure.

Accordingly, the PDSN recognizes that the MS is an MS to which FDCP canbe applied, and performs the FDCP connection procedure including stepsS101 to S105 of FIG. 2.

In this case, when performing the session negotiation with the AN, theMS can include an ID, indicating FDCP as a protocol ID, for example inan enhanced multi-flow packet application parameter, as a protocol IDduring session negotiation with the AN, and then transmit the enhancedmulti-flow packet application parameter.

Although not shown in the drawing, in the case of an MS that does notsupport the FDCP connection procedure in the CDMA2000 HRPD network, theAN transmits service option 59 to the PDSN after the session negotiationbetween the MS and the AN has been performed. In this case, the PDSNperforms a conventional PPP negotiation procedure.

In the above-described fast data call connection method, although thecase where data call connection is performed in response to the requestfrom the PDSN has been described, the case where data call connection isperformed in response to a request from the MS can also be considered.In this case, after the MS has transmitted an FDCP session establishmentrequest message (Request-FDCP-Creation) to the PDSN, the procedureincluding steps S101 to S105 of FIG. 2 is performed.

FIGS. 5 To 7 are flow diagrams of an authentication procedure for datacall connection according to the present invention, which shows anauthentication procedure when an MS supports external authenticationalgorithms.

FIG. 5 is a flow diagram showing an authentication procedure when the MSsupports PAP, an external authentication algorithm.

When transmitting an FDCP response message in the case where the MSsupports PAP, an external authentication algorithm, at step S103, the MSindicates the fact that PAP is a supported authentication algorithm inthe no-authentication option field of the FDCP response message, andthen transmits the FDCP response message (FDCP Ack [No Auth Param, ExtAuth(PAP)]). Then, the MS transmits an FDCP authentication requestmessage (FDCP_Auth_Request), including a peer ID and a password(Peer-ID/PW) to the PDSN at step S103-11.

Accordingly, the PDSN transmits an FDCP authentication response message(FDCP_Auth_Ack) to the MS at step S103-12, and performs authentication.If authentication succeeds, the PDSN transmits an authenticationnotification message (FDCP_Auth_Request [APD(PAP-Success)]), indicatingthat authentication has succeeded, at step S103-13, and the MS transmitsan FDCP authentication response message (FDCP_Auth_Ack) to the PDSN atstep S103-14, thus completing the PAP authentication procedure. The PDSNtransmits an FDCP complete message to the MS at step S105, therebyproviding data service.

FIG. 6 is a flow diagram showing an authentication procedure when the MSsupports CHAP, an external authentication algorithm.

When transmitting an FDCP response message in the case where the MSsupports CHAP, an external authentication algorithm, at step S103, theMS indicates the fact that CHAP is a supported authentication algorithmin the no-authentication option field of the FDCP response message, andthen transmits the FDCP response message (FDCP Ack [No Auth Param, ExtAuth(CHAP)]).

Accordingly, the PDSN transmits an FDCP authentication request messageincluding an encoded CHAP challenge(FDCP_Auth_Request[APD(CHAP-Challenge)]) to the MS at step S103-21.After transmitting a response message (FDCP_Auth_Ack) to the FDCPauthentication request message at step S103-22, the MS transmits an FDCPauthentication request message including an encoded CHAP response(FDCP_Auth_Request[APD(CHAP-Response)]) at step S103-23.

Next, the PDSN transmits an FDCP authentication response message(FDCP_Auth_Ack) to the MS at step S103-24, and then performsauthentication using the CHAP response received from the MS. Ifauthentication succeeds, the PDSN transmits an FDCP authenticationnotification message (FDCP_Auth_Request[APD(CHAP-Success)]), indicatingthe success of authentication, at step S103-25. If a response message(FDCP_Auth_Ack) to the FDCP authentication notification message isreceived from the MS at step S103-26, the CHAP authentication procedureis completed, and the PDSN transmits an FDCP complete message to the MSat step S105, thus providing data service.

FIG. 7 is a flow diagram showing an authentication procedure when the MSsupports EAP, an external authentication algorithm.

When transmitting an FDCP response message in the case where the MSsupports EAP, an external authentication algorithm, at step S103, the MSindicates the fact that EAP is a supported authentication algorithm inthe no-authentication option field of the FDCP response message, andthen transmits the FDCP response message (FDCP Ack [No Auth Param, ExtAuth(EAP)]).

Accordingly, the PDSN transmits an FDCP authentication request message(FDCP_Auth_Request[APD(EAP-Identity-Request)]), requesting an identityfor EAP authentication, to the MS at step S103-31. The MS transmits botha response message (FDCP_Auth_Ack) to the FDCP authentication requestmessage and an FDCP authentication request message including an EAPidentity (FDCP_Auth_Request[APD(EAP-Identity-Response)]) to the PDSN atsteps S103-32 and S103-33.

Thereafter, the PDSN transmits a response message (FDCP_Auth_Ack),responding to the reception of the EAP identity, to the MS, and thentransmits an FDCP authentication request message(FDCP_Auth_Request[APD(EAP-MD5-Challenge-Request)]), requesting anEAP-MD5-challenge, to the MS at steps S103-34 and S103-35.

The MS transmits a response message (FDCP_Auth_Ack) to the PDSN, andthereafter transmits an FDCP authentication request message including anEAP-MD5-challenge response(FDCP_Auth_Request[APD(EAP-MD5-Challenge-Response)]) at steps S103-36and S103-37. The PDSN transmits a response message (FDCP_Auth_Ack) tothe FDCP authentication request message at step S103-38, and thenperforms authentication.

If authentication succeeds, the PDSN transmits an FDCP authenticationnotification message (FDCP_Auth_Request[APD(EAP-Success)]) to the MS atstep S103-39. If a response message (FDCP_Auth_Ack) to the FDCPauthentication notification message is received from the MS at stepS103-40, the PDSN transmits an FDCP complete message to the MS at stepS105, thus providing data service.

Hereinbefore, the fast data call connection method between the MS andthe PDSN using the FDCP protocol has been described. Such a function canbe installed on a recording medium in the form of programs that can beexecuted in the MS and the PDSN.

A recording medium according to an embodiment of the present inventioncan be implemented as a recording medium in which a program to beexecuted in, for example, PDSN, is recorded. The program can beimplemented as a program required to sequentially execute a firstfunction of generating a data call connection request message, includingan authentication type and a challenge value, and transmitting the datacall connection request message to the MS, and a second function ofperforming authentication with reference to a data call connectionresponse message, including a response to the challenge value, when theMS transmits the data call connection response message, and ofgenerating a data call connection complete message and transmitting thedata call connection complete message to the MS if authenticationsucceeds. The implementation of the recording medium is not limited tothe PDSN, but the recording medium can be implemented in any devicecapable of performing a fast data call connection procedure togetherwith the MS.

Furthermore, a recording medium according to another embodiment of thepresent invention can be implemented as a recording medium in which aprogram to be executed in an MS is recorded. The program can beimplemented as a program required to execute a first function ofgenerating and transmitting a data call connection response message,including a response to a challenge value, when the MS receives a datacall connection request message, including an authentication type andthe challenge value, and a second function of receiving a data callconnection complete message and determining that data call connectionhas been completed.

As described above, those skilled in the art will appreciate thatvarious modifications, additions and substitutions are possible, withoutdeparting from the scope and spirit of the invention as disclosed in theaccompanying claims. Therefore, it should be understood that theabove-described embodiments are not limiting, but are only exemplary.The scope of the present invention is defined by the accompanying claimsrather than the detailed description. All changes or modifications thatcan be derived from the meaning and scope of the claims and equivalentconcepts thereof should be interpreted as being included in the scope ofthe present invention.

Industrial Applicability

According to the present invention, the existing 13 or more messagesrequired in a call connection process in a CDMA2000 network can bereduced to 3 messages, so that the connection time can be greatlyreduced, and messages, which are not actually required in three stages(LCP, CHAP and IPCP) used in conventional PPP connection, are omitted,or corresponding steps are simultaneously performed, thus reducingconnection time and increasing the probability of connection success.

Further, the present invention is advantageous in that it checks theversion information of a mobile station before an authenticationprocedure and an IP assignment procedure are performed, so thatauthentication and IP assignment can be performed using a method that ispossible among a conventional PPP connection method and an FDCPconnection method according to the present invention, thus guaranteeingcompatibility even with a mobile station that does not support the FDCPconnection method.

The invention claimed is:
 1. A fast data call connection method betweena Mobile Station and a Node serving packet data in a wireless network,comprising: transmitting a first message containing an authenticationtype and a challenge value thereof to the Mobile Station by the Node;transmitting a second message containing an authentication response tothe authentication type and the challenge value to the Node by theMobile Station; transmitting a third message to the Mobile Station bythe Node, when authentication of the Mobile Station is successfullyperformed by using the authentication response, wherein at least one ofthe second message and the third message contain at least one IP(Internet Protocol) address information assigned for the Mobile Station;and exchanging packet data between the Mobile Station and the Node overa data link in point-to-point protocol (PPP), wherein the data link inthe PPP is connected between the Mobile Station and the Node byexchanging the first message, second message and third message, andwherein the fast data call connection method, before the transmission ofthe first message, further comprises negotiating a session with protocolID, which indicates a fast data call connection, between the MobileStation and an Access Network(AN); sending a service option for the fastdata call connection, to the Node by the AN; and receiving the serviceoption and recognizing the Mobile Station supports fast data callconnection, by the Node.
 2. The fast data call connection methodaccording to claim 1, wherein the authentication type in the firstmessage is CHAP (Challenged Handshake Authentication Protocol).
 3. Thefast data call connection method according to claim 1, wherein the thirdmessage contains an IP compression information.
 4. The fast data callconnection method according to claim 1, wherein the second messagecontains an IP address of the Mobile Station, and the third messagecontains the IP address of the Node.
 5. The fast data call connectionmethod according to claim 1, wherein the second message does not containan IP address, and the third message contains the IP address of theNode.
 6. The fast data call connection method according to claim 5,between the transmission of the third message and the exchange of packetdata, further comprising: transmitting a router notification message tothe Mobile Station by the Node; receiving the router notificationmessage and requesting location registration to the Node by the MobileStation; and performing the location registration of the Mobile Stationand transmitting a location registration reply message to the MobileStation, by the Node.
 7. The fast data call connection method accordingto claim 1, wherein the second message contains an IP address which isset to “0”, and the third message contains the IP address assigned forthe Mobile Station, and the IP address of the Node.
 8. A non-transitorycomputer-readable recording medium for storing a program executed in aNode serving packet data in a wireless network to implement fast datacall connection between a Mobile Station and the Node, the programsequentially executing: a first function of generating a first messagecontaining an authentication type and a challenge value thereof, andtransmitting the first message to the Mobile Station; a second functionof receiving a second message containing an authentication response tothe authentication type and the challenge value from the Mobile Station,and transmitting a third message when authentication of the MobileStation is successfully performed, wherein at least one of the secondmessage and the third message contain at least one IP (InternetProtocol) address information assigned for the Mobile Station; and athird function of exchanging packet data with the Mobile Station over adata link in point-to-point protocol (PPP), wherein the data link in thePPP is connected between the Mobile Station and the Node by exchangingthe first message, second message and third message, and wherein theprogram, before executing the first function, further executes functionsof receiving a service option from an Access Network (AN) whichnegotiates a session with protocol ID, which indicates a fast data callconnection, with the Mobile Station, and recognizing the Mobile Stationsupports fast data call connection.
 9. The non-transitorycomputer-readable recording medium according to claim 8, wherein theauthentication type in the first message is CHAP (Challenged HandshakeAuthentication Protocol).
 10. The non-transitory computer-readablerecording medium according to claim 8, wherein the third messagecontains an IP compression information.
 11. The non-transitorycomputer-readable recording medium according to claim 8, wherein thesecond message contains an IP address of the Mobile Station, and thethird message contains the IP address of the Node.
 12. Thenon-transitory computer-readable recording medium according to claim 8,the program, between the second function and the third function, furtherexecuting: a function of transmitting a router notification message tothe Mobile Station; a function of receiving a request for locationregistration from the Mobile Station; and a function of performinglocation registration of the Mobile Station and transmitting a locationregistration reply message to the Mobile Station.
 13. The non-transitorycomputer-readable recording medium according to claim 8, wherein thesecond message contains an IP address which is set to “0”, and the thirdmessage contains the IP address assigned for the Mobile Station, and theIP address of the Node.
 14. A non-transitory computer-readable recordingmedium for storing a program executed in a Mobile Station to implementfast data call connection between the Mobile Station and a Node servingpacket data in a wireless network, the program sequentially executing: afirst function of receiving a first message containing an authenticationtype and a challenge value thereof from the Node; a second function ofgenerating a second message containing an authentication response to theauthentication type and the challenge value, and transmitting the secondmessage to the Node; a third function of receiving a third message fromthe Node, when authentication of the Mobile Station is successfullyperformed; and a fourth function of exchanging packet data with theNode, wherein at least one of the second message and the third messagecontain at least one IP(Internet Protocol) address information assignedfor the Mobile Station over a data link in point-to-point protocol(PPP), wherein the data link in the PPP is connected between the MobileStation and the Node by exchanging the first message, second message andthird message, and wherein the program, before executing the firstfunction, further executes: negotiating a session with protocol ID,which indicates a fast data call connection, with an Access Network(AN)so that the AN sends a service option for the fast data call connectionto the Node.
 15. The non-transitory computer-readable recording mediumaccording to claim 14, wherein the second message contains an IP addresswhich is set to “0”, and the third message contains the IP addressassigned for the Mobile Station, and the IP address of the Node.
 16. Thenon-transitory computer-readable recording medium according to claim 14,wherein the second message contains an IP address of the Mobile Station,and the third message contains the IP address of the Node.
 17. A fastdata call connection method of a Mobile Station to implement fast datacall connection with a Node serving packet data in a wireless network,comprising: receiving a first message containing an authentication typeand a challenge value thereof from the Node; transmitting a secondmessage containing an authentication response to the authentication typeand the challenge value to the Node; receiving a third message from theNode, when authentication of the Mobile Station is successfullyperformed; and exchanging packet data with the Node, wherein at leastone of the second message and the third message contain at least oneIP(Internet Protocol) address information assigned for the MobileStation over a data link in point-to-point protocol (PPP), wherein thedata link in the PPP is connected between the Mobile Station and theNode by exchanging the first message, second message and third message,and wherein the fast data call connection method, before thetransmission of the first message, further comprises negotiating asession with protocol ID, which indicates a fast data call connection,with an Access Network(AN) so that the AN sends a service option for thefast data call connection to the Node.
 18. The fast data call connectionmethod of the Mobile Station according to claim 17, wherein the secondmessage contains an IP address which is set to “0”, and the thirdmessage contains the IP address assigned for the Mobile Station, and theIP address of the Node.
 19. The fast data call connection method of theMobile Station according to claim 17, wherein the second messagecontains an IP address of the Mobile Station, and the third messagecontains the IP address of the Node.
 20. The fast data call connectionmethod of the Mobile Station according to claim 17, wherein the secondmessage doesn't contain an IP address, and the third message containsthe IP address of the Node.
 21. A fast data call connection methodbetween a Mobile Station and a Node serving packet data in a wirelessnetwork, consisting of: transmitting a first message containing anauthentication type and a challenge value thereof to the Mobile Stationby the Node; transmitting a second message containing an authenticationresponse to the authentication type and the challenge value to the Nodeby the Mobile Station; transmitting a third message to the MobileStation by the Node, when authentication of the Mobile Station issuccessfully performed by using the authentication response, wherein atleast one of the second message and the third message contain at leastone IP (Internet Protocol) address information assigned for the MobileStation; and exchanging packet data between the Mobile Station and theNode, wherein the first and second messages are used for theauthentication of the Mobile Station and the second and third messagesare used for an assignment of an IP address, and wherein the fast datacall connection method, before the transmission of the first message,further comprises: negotiating a session with protocol ID, whichindicates a fast data call connection, between the Mobile Station and anAccess Network(AN); sending a service option for the fast data callconnection, to the Node by the AN; and receiving the service option andrecognizing the Mobile Station supports fast data call connection, bythe Node.